HostMonitor's Main Page Remote Monitoring Agent (RMA) for Windows
Version 1.11
Copyright (c) 2000-2004 KS-Soft
  What's New What's New    Copyright/License/Warranty Copyright/License/Warranty    Download HostMonitor Download    Registration Information Buy Now   

Main Page

HostMonitor
Log Analyzer
HML Manager
RMA for Windows
RMA for Unix
RMA Manager
Telnet Service
Web Service
Replicator

IP-Tools

Remote Monitoring Agent (RMA) is an auxiliary application for HostMonitor. It is included into Advanced Host Monitor package. Enterprise license for Advanced Host Monitor already includes license for 10 installations of the agent. Holders of a Lite, Standard or Professional licenses may buy an additional license for Remote Monitoring Agent separately.


Intro    How to do    Known Problems    System Requirements    Price

HostMonitor 4.0+ can monitor remote networks using Remote Monitoring Agents (RMA). RMA is small application that accepts requests from HostMonitor, performs test and provides information about test result back to HostMonitor.

Why you may need RMA? Here are just several reasons:

  1. RMA increases security of the network. When you have to run the tests such as CPU Usage test or Performance Counters tests on a remote system, HostMonitor must be able to log in to that system with administrators privileges. Instead you may now use an agent installed on that remote system. In this case HostMonitor will not have to log on to that system at all. HostMonitor needs just one TCP port to communicate with the RMA agent (by default it uses #1055 port, however you may set an agent to use any other port).
    Remote Monitoring Agent is also a very useful tool when you have to monitor two (or many) separated networks (connected through Internet). In this case installing just one instance of RMA behind the firewall in network "A" will allow to monitor entire network "A" using the HostMonitor located in the network "B" with just one open TCP port.

  2. RMA decreases the network traffic. E.g. frequent use of "File Integrity" or "Compare Files" tests in an array of remote systems may apply significant load on the network. The more and the bigger files you test the more traffic increase you get. RMA runs locally and sends only the test results to the HostMonitor thus decreasing the amount of network traffic.

  3. RMA simplifies network administration. You no longer need to share drives to perform tests like Drive Free Space, Folder/File Size, File Availability, Count Files, etc

Features:
  • All traffic between RMA and HostMonitor is encrypted.
  • It is possible to customize the list of enabled tests for each of the agents (e.g. living only Count Files and Drive Free Space tests only).
  • You can restrict incoming TCP connections with the list of acceptable addresses.
  • With RMA Manager you may configure, restart and even upgrade agent(s) remotely.

Now available RMA for Windows, Linux and FreeBSD. RMA (on Windows platform) can be started as a regular application or as a Win32 service and perform following test methods:
- Ping
- TCP
- UDP
- UNC
- Drive Free Space
- Folder/File Size
- Count Files
- File/Folder Availability Exists
- File Integrity
- Text Log
- Compare Files
- Process
- Service
- NT Event Log
- CPU Usage
- Performance Counter
- Script
- External
- ODBC

Information about RMA for Linux and FreeBSD platforms available here.

How to install RMA

To install RMA run installation program for Advanced Host Monitor package (hm40.exe). At the stage when installation wizard offers you to chose an installation package, you should select "Custom Install". Then in the list of available components check the box in front of the "RMA for Windows". If you want to install only "RMA for Windows" then uncheck everything except "RMA for Windows".

If you need to install RMA on an array of systems, then the easiest way is to:

  • install it on one system using installation program (see the instructions in previous paragraph)
  • configure an agent (setup timeout, password, list of enabled tests, enable or disable remote management, etc)
  • than simply copy preconfigured agent to all systems. You need to copy just 3 files: rma.exe,   rma_cfg.exe,   rma.ini.

    Note: It is also possible (however you may never need it) to run several instances of RMA on the same system. To do this you have to install several copies of RMA into different folders on the hard drive. Each copy of RMA should then be set to use different TCP port.


    How to configure RMA

    To configure an agent you may use rma_cfg.exe program (after installation it will be located in the same directory where an agent is installed) or you may start an agent and click on "Settings" button on the tool bar. This button launches the same configuration utility which pops up as a new window.

    The left part of the configuration window mostly contains information about an agent. Those fields (from the top to the bottom of the window) are joined into three groups: Agent information, Statistics and Agent status.

    Agent information:
    You are not able to change information shown in grey fields. They show data that was predefined by a software developer.

  • Agent: an internal name of an agent
  • Platform: OS platform that this agent is designed for.
  • Version: the version number of the agent.
  • Developer: the company that created RMA software.
  • Comment: this is the only field available for editing in this section. Here you may specify a comment (actually you may type any text here, it could be a simple recognizable name or an identifier for this agent). This helps to identify agents easier.
    HostMonitor and RMA Manager will display the content of these fields when they work with remote agents.

    Statistics
  • Active remote connections: this is the number of requests that this agent is currently processing.
  • Connections performed: the number of requests processed since last time the agent was started.
  • Connections rejected: the number of requests that have been rejected by the agent since it was started. A rejection may be a result of a connection with invalid password or from an IP address that is not allowed.

    Agent status
    These three fields show the status of an agent as an application or Win32 service (you may start an agent in either of these two modes). Also this section shows you the state of currently edited agent configuration i.e.: are the changes for the current configuration already saved or not. Each field is followed by a corresponding control button:

    • Settings: initially, or after you just have started configuration utility, this field says "Applied". This means that the current settings of RMA were not changed yet. As soon as you start typing in any of the fields available for the user, caption changes to "Modifications are not saved" as a reminder that the current changes for the configuration are not saved and thus are not in effect. Only after you click the button "Apply" the changes will be saved. Note that after you have applied changes the caption returns to "Applied".

    • Application status: says either "Active" when RMA is running as a regular application or "Not Active" when RMA is not running. The button beside this field is correspondingly captioned saying "Activate" when RMA is not running, so it will start RMA if you press it. Caption "Deactivate" on the button means that RMA is currently running as a regular application and if you press the button it will be terminated.
      Note that the configuration utility is a separate application and it may run independently, even when RMA is not running.

    • Service status: On Windows NT/2000/XP agent can be installed as a Win32 service. This field and the button display and control the status of RMA as a Win32 service. "Not installed" means RMA is not installed as a Win32 service. "Installed" means that RMA is already installed as a Win32 service. The button beside the field changes its` caption correspondingly - "Uninstall" when RMA is installed as a Win32 service or "Install" when its not. RMA in a Win32 service mode is loaded automatically at a system startup.

    • Service state: this field is empty when Win32 service is not installed. After the servise was installed the following captions will tell you its status: "STOPPED" means the service is installed but not started. "STARTED" is displayed when the service is running. The button "Start/Stop" allows you to start or stop the service.


    Settings

    Connection parameters
    • Port
      specifies the TCP port number which RMA utilizes to listen for incoming connections. Default setting is #1055.

    • Timeout
      the maximum amount of time (in seconds) that agent will keep waiting for the complete request packet from HostMonitor (after initial TCP connection established) before dropping the connection.

    • Password
      minimum six character length password. Using of an empty password is not permitted. The password is required for every communication session between RMA and HostMonitor or RMA and RMA Manager. All traffic between RMA and HostMonitor or RMA and RMA Manager is encrypted and the password itself is never transmitted through the network without encryption.

    Security settings

    • Accept connections from any IP address
      enabling this option will allow RMA to accept control commands from any IP address (as long as the incoming connection provides correct password)
    • Accept connections from following addresses
      specifies the list of IP addresses. After enabling this option RMA will accept remote connections only from the addresses in this list (password is required as always). Usually you have to add just one address to this list, namely the one for the system where HostMonitor is running.
      To add an address to the list press Insert key, to remove an address from the list press Ctrl+Del, to edit item press Enter or double-click it.

    • Enable following tests
      specifies the list of tests methods allowed for execution by this RMA. To enable a test mark the corresponding check box, to disable a test unmark the box near it.

    • Enable remote management from address
      this option sets the IP address from which it is allowed to control and manage RMA. Using RMA Manager installed on the system with that IP address you will be able to change agent's settings remotely, also you will be able to restart and terminate an agent.
      Note: Instead of single IP address you may specify a list and/or a range of IP addresses. IP addresses in the list should be separated by comma. Dash is used to define a range of addresses. Example: "127.0.0.1,  192.168.13.10 - 192.168.13.99,  165.14.22.1".

    • Enable remote updates from address
      this option allows remote updates of the RMA code (e.g. when a new version is available) from the IP address being provided. You may provide single IP address or you may specify a list and/or a range of IP addresses. IP addresses in the list should be separated by comma. Dash is used to define a range of addresses. Example: "127.0.0.1,  192.168.13.10 - 192.168.13.99,  165.14.22.1".
      To upgrade an array of remote agents you may use RMA Manager.

    Logging

    • Successful audit log to
      here you may specify a log file where agent will store information about successfully accepted connections. This log has no use when everything works well (it then just takes space on the hard drive), but you may found it really helpful when a sophisticated network problem has to be fixed. If you specify just the name of the file (without a full path), an agent will store a log in the same directory where it was started from.

    • Failure audit log to
      you may specify another log file where an agent will store information about rejected requests. E.g.: connections from an IP addresses that are not allowed or connections with invalid password, etc. Log file is a simple text file that contains date of the event, remote IP address from which an attempt of connection has occurred and information about the error. If you specify just the file name (without path), an agent will store it in the directory where it was started from.


    RMA Manager
    To configure huge arrays of remote agents installed in different networks you may use RMA Manager. It allows you to change settings for hundreds of agents installed on remote systems at one time and from one comfortable location.


    How to use

    O.k., now when you have your agents installed in different networks, how to use them?
    HostMonitor since version 4.0 supports a list of remote agents and can perform tests not only by itself but also may send a request to the agent which will then execute the test. Every test in HostMonitor has now an additional property: "Test by". By default it has the value "HostMonitor"; it means that the test will be executed by HostMonitor. Alternatively you may choose an agent from drop down list and the test will be performed by that agent.


    Known problems:

    Windows 95, 98, ME, NT Workstation, 2000/XP Professional has a serious limitation: maximum length of the queue for pending TCP connections is limited to 5 items.
    This limitation creates problems when you want to perform lots of tests by a single remote agent (e.g. monitoring many systems by a single agent that is installed on the system in the remote network).

    Suggested solution:
    To avoid possible rejections of requests caused by the queue overflow you should:


    Minimum system requirements

    • Windows 95 (OSR2), 98, ME, NT 4.0, Windows 2000, or XP
    • TCP/IP connection (LAN or Dial-up)
    • 2 Mb of free disk space
    Recommended:
    • Windows 2000

    How much does it cost?

    When you purchase an Advanced Host Monitor ENTERPRISE edition you will get the license for 10 installations of the agent at no cost. Otherwise you may buy licenses in sets of 10 ($80 per 10 licenses) or in sets of 100 licenses ($300 per one set of 100). You may order Remote Monitoring Agent using credit card, Switch and Solo debit cards, check/money order or wire transfer. If you are concerned about submitting your order and/or credit card information online, you may order the license via phone, fax or postal mail.
    Details..